Module 9  Spring 2006 closure
Prepared by Greg Kinney

Most meaningful

 

 

Muddiest

Instructor reply:  No question to reply to.

Instructor reply:  Yes – this topic is covered in statistics textbooks but isn’t here.  When you’re using a Z value in a normal probability distribution, you are interested in the cumulative probability of the distribution to the left of the z value.  Let’s say there are two values, +z and –z, where –z is just the negative of +z.  Then if P represents the single tail (left hand) probability that you find in Table 8-5, then the probability associated with –z turns out to be (1-P).  For instance, at z = 0.20, P = 0.5793.  For z = -0.20, P = (1-0.5793) = 0.4207.  An easy way to calculate this – easier than using Table 8-5 – is to go into Excel and use the NORMSDIST function.  All you do is input your value of z, positive or negative, and it spits out the answer.

There is much more to know about this and I really don’t recommend relying on Excel as a substitute for understanding this.  If you can see your way clear to do it, AS 307/308 are terrific courses for understanding the fundamentals, and the Statistics for ESM course is an excellent applied course.  The way engineering is evolving, we are all going to have to get much better at this.

 

Instructor reply:  A course in statistics, and then another course in statistics, will clear up a lot of the mystery around this.  I recommend these strongly.  Apart from that, part of the problem has to be the fact that Microsoft Project doesn’t handle simulations internal to the package.  Some project management software now does.  So you have to get out of Microsoft Project anad the get into the Crystal Ball package in order to get anywhere.  This is confusing, and that part of it would be better just with some practice.
I wouldn’t get too hung up about Crystal Ball right now, though.  It’s a great tool, and one that you can use to try to estimate how interacting uncertainties may accumulate.  It’s a much better approach than the old “factor of safety” rules of thumb we’ve always had.  But this is a first course only.

 

Instructor reply:  I am not the best person to explain this, but I can see what they’re doing here.  Looking at the caption, the “RIGHT!!!” diagram makes explicit the precedence relationships that are assumed here.  In the “WRONG!!!” diagram, a dummy leg goes from node 1 to node 2.  A second dummy node goes from node 2 to node 3.  The implication is that activity “a” as well as “b” and “c” precedes “f”; however, in this example, “f” is only supposed to depend on “b” and “c”.  However, “a” precedes both “d” and “e” and “e” is preceded by both “a” and “b”; thus, the dummy leg must be inserted as shown in order for the logical relationship to be correct.  Again, this comes straight off the caption.  Note that there is a typo in the paragraph on p. 380 where it’s referencing this diagram.  The description really gums it up to the point where it’s incomprehensible without looking at it closely.

 

Instructor reply:  PMI comes down hard on the side of updating project schedules and baseline schedules.  The baseline schedule is what the planned schedule originally was, or if an approved change is made, it is an updated baseline that reflects the results of that change.  In case where there is a significant change to the project timeline for whatever reason, the schedule should be updated and a revised schedule (with a revised finish date) must be approved.  Of course in many cases this slippage can be to the detriment of a PM’s career.  The updated schedule will need to reflect the new network, if there is a change to the critical path.  So, the answer is that there is no rule of thumb as to how often to do this, except the answer is “never” if (as is desired) the project schedule remains intact.  But if something changes, the Gantt chart and network should be updated per PMI.  Also of note is that it is often good practice to update the Gannt chart with the actual vs. the planned progress.

Of course, in large projects it’s common for the critical path to flip from one thing to another, and it can be really very taxing on everybody to monitor all this.  See Dr. Perkins’ comments on just this problem in the Old Closure of Module 9.

 

Instructor reply:  You can use the “link tasks” button on the toolbar to graphically connect activities in the Gantt chart.  You can’t do it on the network diagram to my knowledge.  There are other programs (a simulation language called iThink comes to mind) where you can and do link “nodes” using a mouse as you’re suggesting.  Maybe someday someone can create an aftermarket product that does what you’re suggesting.  I think a lot of us would appreciate it.

 

Instructor reply:  I think this is personal preference.  The advantage of AON is that the software packages go in that direction.  The appeal of AOA, for me at least, is that there is something that feels a little better about the use of an arrow length to represent a duration, even though you can’t draw the arrow to a time scale in any practical sense.  Someday I plan to read an old text of mine that gets into arrow diagramming methods so I can get a little more insight as to why AOA (a/k/a ADM) might have advantages.